FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.ehrs.ehrsfmr21#current (16 ms)

Package hl7.ehrs.ehrsfmr21
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CPS.2.6.html
Url http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.2.6
Version 2.1.0
Status active
Date 2024-11-26T16:30:50+00:00
Name CPS_2_6_Support_Patient_Health_Data_Derived_from_Administrative_and_Financial_Data_and_Documentation
Title CPS.2.6 Support Patient Health Data Derived from Administrative and Financial Data and Documentation (Function)
Experimental False
Realm uv
Authority hl7
Description Capture and explicitly label patient health data derived from administrative or financial data; and link the data source with that data.
Purpose It is critically important to be able to distinguish patient health data derived from administrative or financial data from clinically authenticated data.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Statement N:

Capture and explicitly label patient health data derived from administrative or financial data; and link the data source with that data.

Description I:

It is critically important to be able to distinguish patient health data derived from administrative or financial data from clinically authenticated data.

Criteria N:
CPS.2.6#01 SHALL

The system SHALL provide the ability to capture, store and render patient health data derived from administrative or financial data and tag it as such.

CPS.2.6#02 SHOULD

The system SHOULD provide the ability to capture, store, and render, the source of patient health data derived from administrative and financial data.

CPS.2.6#03 SHOULD

The system SHOULD provide the ability to annotate patient health information derived from administrative or financial data (e.g., by providing text-based comments, attaching a picture of an injury, or attaching an image of a supporting document).


Source

{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-CPS.2.6",
  "meta" : {
    "profile" : [
      "http://hl7.org/ehrs/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Capture and explicitly label patient health data derived from administrative or financial data; and link the data source with that data.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>It is critically important to be able to distinguish patient health data derived from administrative or financial data from clinically authenticated data.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.6#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture, store and render patient health data derived from administrative or financial data and tag it as such.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.6#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture, store, and render, the source of patient health data derived from administrative and financial data.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.6#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to annotate patient health information derived from administrative or financial data (e.g., by providing text-based comments, attaching a picture of an injury, or attaching an image of a supporting document).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.2.6",
  "version" : "2.1.0",
  "name" : "CPS_2_6_Support_Patient_Health_Data_Derived_from_Administrative_and_Financial_Data_and_Documentation",
  "title" : "CPS.2.6 Support Patient Health Data Derived from Administrative and Financial Data and Documentation (Function)",
  "status" : "active",
  "date" : "2024-11-26T16:30:50+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Capture and explicitly label patient health data derived from administrative or financial data; and link the data source with that data.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "purpose" : "It is critically important to be able to distinguish patient health data derived from administrative or financial data from clinically authenticated data.",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-CPS.2.6-01",
      "label" : "CPS.2.6#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to capture, store and render patient health data derived from administrative or financial data and tag it as such.",
      "derivedFrom" : "EHR-S_FM_R1.1 DC.1.1.3.3#1"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-CPS.2.6-02",
      "label" : "CPS.2.6#02",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to capture, store, and render, the source of patient health data derived from administrative and financial data.",
      "derivedFrom" : "EHR-S_FM_R1.1 DC.1.1.3.3#2"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-CPS.2.6-03",
      "label" : "CPS.2.6#03",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to annotate patient health information derived from administrative or financial data (e.g., by providing text-based comments, attaching a picture of an injury, or attaching an image of a supporting document)."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.